Host network analyzer

ABSTRACT

Systems and method for generating a network configuration model for a host computer system are disclosed. An example method may include querying a host computer system for network configuration data. The method further includes receiving, in response to the querying, the network configuration data including configuration data of network components included by the host computer system and configuration data of connectivity between the network components. At least one of the network components may be represented by a virtual network component. The method also, generates, in view of the network configuration data, a network configuration model.

TECHNICAL FIELD

Embodiments of the present invention relate generally to virtualizedcomputer systems and more specifically related to generating a networkconfiguration model for a host virtual machine.

BACKGROUND

Network virtualization may be software-emulated representations ofphysical network components of physical network infrastructure used toprovide corresponding virtual network components to a host computersystem. The host computer system may execute a host operating system(OS) to run an application container. A host computer system may alsoexecute a hypervisor to run one or more virtual machines (VM). The hostcomputer system may be used for network virtualization. The hostcomputer system may include both physical and virtual network componentsto be used for network virtualization. Physical network components mayinclude networking hardware such as routers, bridges, switches, andnetwork interface cards (NICs) used to facilitate the transmission ofdata in a computer network. Virtual network components may besoftware-emulated representations of corresponding physical networkcomponents.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, and can be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 is a block diagram that illustrates an embodiment of a computersystem that hosts one or more application containers, in accordance withone or more implementations of the present disclosure.

FIG. 2 is an illustration of a graphical. representation of a networkconfiguration model, in accordance with some implementations of thepresent disclosure.

FIG. 3 is a flow diagram illustrating a method of generating a networkconfiguration model of a host computer system, in accordance with someimplementations of the present disclosure.

FIG. 4 is a flow diagram illustrating a method of querying for networkconfiguration data of a host computer system, in accordance with someimplementations of the present disclosure.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system, in accordance with someimplementations of the present disclosure.

DETAILED DESCRIPTION

Described herein are methods and systems of generating a networkconfiguration model by querying a host computer system for networkconfiguration data of one or more virtual network components.

“Application container” or “container” herein shall refer to a softwarecomponent providing an interface between a host and a softwareapplication. An application container may provide resource isolation forresources (e.g., applications, network components, etc.) associated withthe application container. For example, virtual network componentsassociated with an application container may be isolated from othervirtual network components associated with another application containerand/or virtual machine. The software application may comprise one ormore related processes and may provide a certain service (e.g., an HTTPserver, a database server, etc.). The host may be represented by a hostcomputer system or by a virtual machine being executed by a hostcomputer system. In the containerized execution model, the softwareapplication and its dependencies (such as binaries and/or libraries thatas necessary to run the application) run within the applicationcontainer, which is an isolated process in the user space of the hostoperating system, sharing the kernel with other containers. Anapplication container may be run directly on the host OS and may be runwithout a hypervisor. Application container may refer to an applicationcontainer and/or a virtual machine. A virtual machine may be a type ofapplication container.

A “virtual machine” (also may be referred to as “VM”) may be asoftware-emulated representation of a physical machine, such as acomputer system. A virtual machine may be run by a hypervisor executedby a host computer system.

“Network configuration data” herein shall refer to parameters and valuesof the parameters describing the network components included by a hostcomputer system and describing the connectivity between the networkcomponents. The network configuration data may include configurationdata of one or more virtual network components.

“Connectivity” herein shall refer to a path of a network frame betweenat least two Open Systems Interconnection (OSI) data link layer (layer2) network components or a path of a data packet between at least twoOSI network layer (layer 3) network components. The OSI model may be aconceptual model that characterizes and standardizes the internalfunctions of a communication system, such as host computer system 100,by partition the communication system into abstract layers (i.e., layers1-7). The data link layer (layer 2) may be the protocol layer thattransfers data between adjacent network nodes and may be responsible foraccess control, flow control, and error checking. Examples of data linkprotocols may be Ethernet, Point-to-Point Protocol, High-Level and DataLink Control, among others. A path of a network frame between two OSIdata link layer network components may, for example, the path of a framefrom one virtual Ethernet interface of a VM to another virtual Ethernetinterface of another VM (e.g., a virtual Ethernet interface pair). Thenetwork layer (layer 3) may provide functional and procedural rules oftransferring data sequences from a source to a destination node and maybe responsible for packet forwarding. Internet Protocol and IP addressesmay be part of the network layer. A path of a data packet between twoOSI network layer network components may, for example, be the path of adata packet from one virtual router to another virtual router.

A “network interface card” (also may be referred to as “networkinterface controller” or “NIC”) herein shall refer to a computerhardware component that connects a computer system to a computernetwork. A NIC may operate on both the physical and data link layers ofa computer system and allow network connectivity. A host computer systemmay have one or more NICs. One or more virtual NICs may be logicallyconnected to one physical NIC. Each NIC may be associated with a uniquemedia access control (MAC) address.

A “virtual network interface card” (also referred to as “virtual networkinterface controller” or “vNIC”) herein shall refer to asoftware-emulated representation of a physical NIC that may act as aphysical NIC for an application container and/or virtual machine. Anapplication container and/or VM with a network interface may have a vNICassociated with a unique MAC address.

A “virtual network” (also referred to as “network virtualization”)herein may refer to a software-emulated representation of one or morephysical network components.

A “virtual network segment” herein may refer to a software-emulatedrepresentation of a physical network segment (e.g., a LAN segment).

A “network configuration model” herein may refer to a representation ormathematical structures describing relationships between objects, suchas network components. One example of a network configuration model maybe a graph including a finite set of nodes at least some of which areconnected by edges. In one example, the nodes may represent networkcomponents of a host computer system, while the edges may represent theconnectivity between network components modeled as edges.

In accordance with one or more implementations of the presentdisclosure, a host network analyzer component may be a softwareapplication implementing one or more features of the systems and methodsof the present disclosure. In one implementation, a host networkanalyzer component may query a host computer system for networkconfiguration data. Querying for network configuration data may includequerying the host machine to find the containers and/or VMs associatedwith the host machine. Host network analyzer component may query certainapplication containers and/or VMs to discover the network componentsassociated with such an application container and/or VM. One or more ofthe network components may be virtual network components. To discoverthe network components, the host network analyzer component may query atleast one of the host OS (e.g., kernel of the host OS), guest OS (e.g.,kernel of the guest OS) of a VM, or the hypervisor. In some cases, todiscover additional network components the host network analyzercomponent may query applications (e.g., daemons) using applicationprogramming interface (API) calls. For each network component associatedwith the containers and/or VMs (and/or for each network componentassociated with a virtual network e.g., all network componentsassociated with the host computer system), the host network analyzercomponent may determine the connectivity between the network components.To determine the connectivity, host network analyzer component may queryat least one of the host OS, guest OS of a VM, or hypervisor. Todetermine additional connectivity between network components, hostnetwork analyzer component may query applications (e.g., daemons)operating in user space (or split between user and the kernel) using APIcalls. The network configuration data for the network components and theconnectivity between the network components may be used to generate anetwork configuration model describing the network configuration of thehost computer system.

Various aspects of the above referenced methods and systems aredescribed in details herein below by way of examples, rather than by wayof limitation.

FIG. 1 is a block diagram that illustrates an embodiment of a computersystem (referred to herein as a host computer system 100) that hosts oneor more application containers (VM 115-116, Container 117-118). The hostcomputer system 100 may be a rackmount server, a workstation, a desktopcomputer, a notebook computer, a tablet computer, a mobile phone, apalm-sized computing device, a personal digital assistant (PDA), etc.The host computer system 100 includes host hardware 105, which mayinclude multiple processing devices 120, 122, multiple devices 124, 126,memory 128, physical network interface controllers (NICs) 129, networkcomponents 130, and other hardware components. The memory 128 mayinclude volatile memory devices (e.g., random access memory (RAM)),non-volatile memory devices (e.g., flash memory), and/or other types ofmemory devices. The host hardware 105 may also be coupled to externalstorage 132 via a direct connection or a local network. The hostcomputer system 100 may be a single machine or multiple host computersystems arranged in a cluster.

Network component 130 may be a single network device or multiple networkdevices. Examples of network devices include ports, bridges (which mayconsist of multiple ports), tunnels, switches, routers, and otherphysical network devices.

Each of the devices 124, 126 may be a physical device that is internalor external to the host computer system 100. Examples of internaldevices include a graphics card, hardware RAID controller, secondarystorage (e.g., hard disk drive, magnetic or optical storage based disks,tapes or hard drives), universal serial bus (USB) devices, internalinput/output (I/O) devices, etc. Examples of external devices include akeyboard, mouse, speaker, external hard drive (e.g., external storage132), external I/O devices, etc.

The NIC 129 may be a single NIC or may be multiple NICs. NIC 129 may beEthernet controllers, Wi-Fi controllers, Token Rings, and so forth. TheNICs 129 provide functionality to communicate over a network usingspecific physical layer (OSI layer 1) and data link layer (OSI layer 2)standards (e.g., Ethernet, Wi-Fi, Token Ring, etc.).

The host computer system 100 includes a hypervisor 140 (also known as avirtual machine monitor (VMM)). In one embodiment (as shown) hypervisor140 is a component of a host operating system (OS) 110. Alternatively,the hypervisor 140 may run on top of a host OS 110, or may run directlyon host hardware 105 without the use of a host OS 110.

The hypervisor 140 may manage system resources, including access tomemory 128, devices 124, 126, NICs 129, secondary storage, and so on.Alternatively, hypervisor 140 may rely on the host OS 110 to manage thesystem resources. The hypervisor 140, though typically implemented insoftware, may emulate and export a bare machine interface (host hardware105) to higher level software. Such higher level software may comprise astandard or real-time operating system (OS), may be a highly strippeddown operating environment with limited operating system functionality,may not include traditional OS facilities, etc. The hypervisor 140presents to other software (i.e., “guest” software) the abstraction ofone or more virtual machines (VMs) 115-116, which may provide the sameor different abstractions to various guest software (e.g., guestoperating system, guest applications, etc.).

Application containers 117-118 may run directly on a host OS 110 withouta using a hypervisor. The containers may share the host OS andunderlying physical resources. Network configuration data for acontainer 117-118 may be obtained by querying the host OS using systemcalls defined by, for example, an application binary interface (ABI). AnABI may define a system call interface allowing user space programs,such as software applications operating in containers 117-118, toexecute kernel-level functions of the host OS 110. Numerous system callsare typically available to the user space program via the ABI. A systemcall may provide a way for an application to request a service from akernel of host OS 110. In other implementations, an ABI may not berestricted to the kernel.

Network configuration data for network components associated with VMs,such as VM 115-116, may be obtained from the hypervisor and/or the guestOS (e.g., kernel) of the respective VM. The hypervisor may be queriedusing function calls or API calls to the hypervisor. The guest OS of aVM may be queried using system calls associated with the respectivequest operating system.

The host computer system 100 hosts any number of virtual machines (VM)115-116 (e.g., a single VM, one hundred VMs, etc.) and/or containers117-118. A virtual machine 115-116 is a combination of guest softwarethat uses an underlying emulation of host computer system 100 (e.g., asprovided by hypervisor 140). Each VM 115-116 and/or container 117-118may include one or multiple virtual components such as virtualprocessors, virtual memory, virtual devices (e.g., virtual storage),virtual NICs 160-163, and virtual network components such as virtualports, virtual bridges (which may contain virtual ports), virtualtunnels, and so forth. Each of these virtual components may map to ahardware component, such as a processing device 120, 122, device 124,126, external storage 132, NIC 129, memory 128, or network component130. Virtual machines 115-116 may be, for example, hardware emulation,full virtualization, para-virtualization, and operating system-levelvirtualization virtual machines. The guest software that runs in a VM115-116 may include a guest operating system, guest applications, guestdevice drivers, etc. The virtual machines 115-116 may have the same ordifferent guest operating systems, such as Windows®, Linux®, Solaris®,etc.

Some virtual machines 115-116 and/or containers 117-118 may includesoftware that is accessible by clients (e.g., local clients and/orremote clients) to provide services to those clients. For example, VM115 may include a virtual server such as a virtual web server, a virtualdata storage server, a virtual gaming server, a virtual enterpriseapplication server, a virtual voice over internet protocol (VOIP)server, etc. A client may connect to the virtual sever to request one ormore services provided by the virtual server.

Similarly, some VMs 115-116 and/or containers 117-118 may include avirtual desktop. A virtual desktop is a virtualized desktop computer,and thus may include storage, an operating system, applicationsinstalled on the operating system (e.g., word processing applications,spreadsheet applications, email applications, etc.), and so on. However,rather than these functions being provided and performed at a client,they may instead be provided and performed by VM 115-116 and/orcontainer 117-118. A virtual desktop may represent an output (e.g., animage to be displayed) generated by a desktop application running withina virtual machine. Graphics data associated with the virtual desktop canbe captured and transmitted to a client, where the virtual desktop maybe rendered by a rendering agent and presented by a client application.

Some virtual machines 115-116 and/or containers 117-118 may includesoftware that performs one or more functions transparently to a virtualserver, virtual desktop and/or client. For example, virtual machines115-116 may include virtual appliances. A virtual appliance may be avirtual machine image file that includes a preconfigured operatingsystem environment and a single application. A virtual appliance maysimplify the delivery, setup and operation of that single application.Virtual appliances may be used for deploying network applications, suchas firewalls, virtual private networks, wide area network (WAN)optimizers, and so forth.

Host computer system 100 may include host network analyzer component168A-C. In one implementation host network analyzer component (e.g.,host network analyzer component 168A) may be a software applicationrunning on host OS 110. In another implementation, host network analyzercomponent 168A may be a component of host OS 110. In anotherimplementation, host network analyzer component (e.g., host networkanalyzer component 168B and/or 168C) may be an application installed ona VM or container, such as VM 115-116 and container 117-118. In stillanother implementation, host network analyzer component may be asoftware application running outside the host computer system 100, suchas at a host controller. Any combination of the aforementioned examplesmay be implemented. References to host network analyzer component 168Awill be made below for purposes of illustration rather than limitation.Host network analyzer components 168B-C may have similar functionalityand implementation as described with respect to host network analyzercomponent 168A, unless otherwise indicated.

In one implementation, host network analyzer component 168A may query ahost computer system 100 for network configuration data. The hostnetwork analyzer component 168A may query at least one of a host OS 110(e.g., kernel) using system calls, guest OS (e.g., kernel) of VM 115-116using system calls, or hypervisor 140 using calls, such as functioncalls or API calls. It should be noted that in some implementations,host network analyzer component 168A may query the hypervisor 140 orkernel of guest OS for network configuration data in regards to VM 115and 116 and/or may query the kernel of host OS 110 using system callsfor network configuration data in regards to container 117 and 118. Instill another implementation, host network analyzer component 168A maycommunicate with host network analyzer component 168B and/or 168Cassociated with VM 115 and VM 116, respectively, to gather networkconfiguration data for the respective VMs. Host network analyzercomponent 168A may communicate with host network analyzer component 168Band/or 168C through hypervisor 140 (e.g., using system calls) and/orthrough a vNIC (e.g., vNIC 160 and/or 161 and using calls, such asfunction or API calls to host network analyzer component 168B and/or168C). Host network analyzer components 168B and/or 168C may gathernetwork configuration data for each of the associated VMs andcommunicate the network configuration data to host network analyzercomponent 168A on host OS 110. Host network analyzer component 168A mayaggregate the received network configuration data from host networkanalyzer components 168B and/or 168C (as well as any additional networkconfiguration data) and use the aggregated network configuration data togenerate a network configuration model.

As part of querying host computer system 100 for network configurationdata, host network analyzer component 168A may query the host computersystem 100 to determine the VMs and containers operating on hostcomputer system 100. As described the above, host network analyzercomponent 168A may query at least one of the host OS 110, guest OS of aVM, or a hypervisor. In response to the query, host network analyzercomponent 168A may receive an identifier for each container 117 and 118and VM 115 and 116 operating on host computer system 100.

For each container and VM, host network analyzer component 168A mayquery the host computer system 100 for configuration data of networkcomponents used by each container and/or VM. To query for configurationdata of network components, host network analyzer component 168A mayquery at least one of host OS 110, guest OS, and/or hypervisor 140 todetermine the network components included by each container and VM. Insome implementations, host network analyzer component 168A may lookoutside the kernel and/or hypervisor for some or all the configurationdata of some or all the network components. In such instances, hostnetwork analyzer component 168A may query one or more applications (ordaemons) running in user space (or split between running in user spaceand the kernel) using API calls specific to a particular application.The configuration data for the network component may include parametersand values indicating the type of network component (e.g., vNIC, virtualEthernet interface, etc.), the version of the network component, thename of the network component, the Internet Protocol (IP) address of thenetwork component, the MAC address of the network component, the netmaskassociated with the network component, the default gateway associatedwith the network component, state of the network component (e.g.,administratively enabled or disabled, link detected, promiscuous mode,multicast mode enabled, etc.), traffic filter configuration, quality ofservice (QoS) configuration, routing information associated with anetwork component, among other configuration information.

In some implementations, one or more of the network components may be avirtual components provided by vNIC associated with a container (e.g.,vNIC 160 associated with VM 115 and/or vNIC 162 associated withcontainer 117). For example, the virtual components provided by the vNIC160 may be a virtual Ethernet interface at VM 115. A virtual componentmay also be provided by a virtual network segment associated with thevNIC such as a virtual switch at host OS 110 sending data to one or morevNICs 160-163.

For each network component of a VM and/or container, host networkanalyzer component 168A may query the host computer system 100 forconfiguration data describing the connectivity between networkcomponents. To query for connectivity configuration data, host networkanalyzer component 168A may query at least one of the host OS 110 (e.g.,kernel), guest OS (e.g., kernel) of the VM, or the hypervisor 140. Insome implementations, host network analyzer component 168A may lookoutside the kernel and/or hypervisor for some or all the configurationdata of some or all the network components. In such instances, hostnetwork analyzer component 168A may query one or more applications (ordaemons) running in user space (or split between running in user spaceand the kernel) using API calls specific to a particular application. Inone example, if host network analyzer component 168A knows the type ofnetwork component identified from configuration data, host networkanalyzer component 168A may employ a module for the specific type ofnetwork component. The module may execute a series of instructions andquery a combination of kernel, hypervisor, and/or application for thespecific type of network component to determine configuration dataindicating the connectivity of the network component. The configurationdata for the connectivity may include parameters and values indicating apath of a network frame between at least two OSI data link layer (layer2) network components, path of a data packet between at least two OSInetwork layer (layer 3) network components, the destination networkcomponent for a frame, the origin network component of a frame, whetheror not the network component changes the header of a frame (e.g., add aVLAN tag) upon sending the frame, among other information. Theconfiguration data for the connectivity may further include parametersand values indicating that the connectivity between two networkcomponents is conditional. Conditional connectivity may refer to a patha network frame and/or data packet may take if certain conditions (e.g.,based on network frame header and/or data packet header and/or networkframe content and/or data packet content) are fulfilled. For example,only a data packet with a certain VLAN ID may be received through aparticular path. It should be noted that conditions may not be symmetricfor transmission and reception.

It should also be noted that host network analyzer component 168A maydetermine the connectivity between network components associated withhost computer system 100 (e.g., not only for network componentsassociated with containers and/or VMs). The host network analyzercomponent 168A may query the hypervisor 140 (or another application) todetermine configuration data of the network components associated withhost computer system 100, in a similar manner as described herein. Alsoin a similar manner as described herein, host network analyzer component168A may determine configuration data of the connectivity between thenetwork components associated with host computer system 100. Forexample, a host computer system 100 may be associated with a complextopology of interconnected bridges (e.g., virtual bridges and/orphysical bridges). Host network analyzer component 168A may determinethe bridges associated with host computer system 100 and not onlydetermine the connectivity between, for example a virtual networkcomponent associated with a VM and the bridge, but also determine theconnectivity between the multiple bridges themselves.

The network configuration data may be used to generate a networkconfiguration model for host computer system 100. In one example,network components may be represented by nodes of a graph and theconnectivity between network components represented by edges of a graph.The network configuration model may be of all or part of the networkcomponents included by the host computer system 100.

In one implementation, the network configuration model may reflect adata link layer (layer 2) and/or a network layer (layer 3) of the OpenSystems Interconnection (OSI) model.

In another implementation, the network configuration model may reflectone or more of the 7 layers of the OSI model. For example, the networkconfiguration model may include the application layer (layer 7). Theapplication layer may specify shared protocols and interface methodsused by hosts in a network. The network configuration model may include,for example, a web browser with a proxy, as a node.

The network configuration model may be used for various purposes. In oneimplementation, the network configuration model may be used to generatea graphical representation of the network configuration for hostcomputer system 100. The graphical representation may be displayed on auser device, such as client machine. An example of a graphicalrepresentation of the network configuration model of a host computersystem is provided in FIG. 2.

In another implementation, the network configuration model may be usedto simulate network traffic on the host computer system. Network trafficmay include multiple frames (e.g., layer 2). It should be noted thedescription of the data link layer (layer 2) is used for purposes ofillustration and not limitation. Descriptions of network traffic (e.g.,data packets of layer 3), or other features described herein, may useelements of other layers of the OSI model. In one implementation,simulating network traffic may include a user providing input. Forexample, using a user interface a user may input a data packet (e.g., ofa particular type) at a particular node. The network configuration modelmay be used to determine which path and/or paths the data packet maytake, which nodes the data packet will visit, and/or how the data packetmay be modified at each node along the path (e.g., adding a VLAN tag ata VLAN networking component). A data packet may take multiple paths, andeach path may be simulated and the results reported. The result may bedisplayed as a chain of nodes and edges (e.g., indicating a path) and/orgraphically (e.g., such as depicted with reference to FIG. 2). Thesimulation may be based on the network configuration model and performedwithout sending an actual data packet on host computer system 100. Thesimulation may be performed on a different computer system (or same)from which the network configuration data was gathered (e.g., by savingthe network configuration model to a file and transporting the file to adifferent computer system).

In still another implementation, the network configuration model may beused to analyze the network configuration on the host computer system.Analyzing the network configuration on the host computer system mayinclude analyzing the type of network frames and/or data packets thatmay pass between two nodes of the network configuration model. Analyzingthe network configuration may also include analyzing the average maximumrate at which network frames and/or data packets may be sent between twonodes. The analysis may be based on the network configuration model andperformed without sending an actual data packet or network frame on hostcomputer system 100. The analysis may be performed on a differentcomputer system (or same) from which the network configuration data wasgathered (e.g., by saving the network configuration model to a file andtransporting the file to a different computer system).

FIG. 2 is an illustration of a graphical. representation 200 of anetwork configuration model, in accordance with some implementations ofthe present disclosure. Graphical representation 200 includes nodes210-221. Each node represents a network component of host computersystem 100. Each node may contain additional information, such aconfiguration data, for the respective network component. For example,node 210 includes the name of the network component (i.e., name 250),the type of network component (i.e., network component 251 indicates aphysical NIC), an address 252 (e.g., IP address, MAC address, etc.).Each node may convey additional configuration data by, for example,using colors. A node colored green may indicate that the respectivenetwork component is enabled and a node colored grey may indicate thatthe respective network component is disabled (e.g., disabled by anadministrator).

Graphical representation 200 also includes edges 240-247. An edge mayrepresent configuration data of the connectivity between two networkcomponents. Edges may be dashed to show a possible network traffic flowbetween two network components (e.g., edge 244) disabled by, for examplean administrator. An edge may have a label, such as label 260-262identifying a destination network component for a frame. Edges withlabels (e.g., edge 240 and edge 241) may indicate that only frames of aparticular type may be sent between the two network components. Edgeswithout a traffic label (e.g., edge 242 and 243) may indicate thatframes of any particular type may be sent between two networkcomponents.

Nodes may be logically grouped. For example, grouping 230 includes allthe network components (e.g., nodes 212-214) of container 117 of FIG. 1,and grouping 231 contains all the network components (e.g., nodes216-218) of container 118 of FIG. 1.

FIG. 3 is a flow diagram illustrating a method of generating a networkconfiguration model of a host computer system, in accordance with someimplementations of the present disclosure. Method 300 may be performedby processing logic that may include hardware (circuitry, dedicatedlogic, etc.), software (such as is run on a general purpose computersystem or a dedicated machine), or a combination of both. In oneimplementation, the method 300 is performed all or in part by hostnetwork analyzer component 168A, 168B, and/or 168C.

In block 305 of method 300 where processing logic implementing themethod queries host computer system 100 for network configuration data.Method 300 continues in block 310 where processing logic in response tothe query receives the network configuration data. Method 300 continuesto block 315 where processing logic generates a network configurationmodel in view of the network configuration data. Method continues toblock 320 where processing logic causes a graphical representation ofthe network configuration model to be displayed on a user device. Method300 is further described in reference to FIGS. 1 and 2, above.

FIG. 4 is a flow diagram illustrating a method of querying for networkconfiguration data of a host computer system, in accordance with someimplementations of the present disclosure. Method 400 may be performedby processing logic that may include hardware (circuitry, dedicatedlogic, etc.), software (such as is run on a general purpose computersystem or a dedicated machine), or a combination of both. In oneimplementation, the method 400 is performed all or in part by hostnetwork analyzer component 168A, 168B, and/or 168C.

Method 400 begins at block 405 where processing logic implementing themethod receives an identifier of an application container included bythe host computer system. Method 400 continues to block 410 whereprocessing logic queries the host computer system for configuration dateof the network components used by the application container. Method 400continues to block 415 where processing logic queries the host computersystem for configuration data of the connectivity between the networkcomponents. Method 400 is further described in reference to FIGS. 1 and2, above.

For simplicity of explanation, the methods 300 and 400 are depicted anddescribed as a series of acts. However, acts in accordance with thisdisclosure can occur in various orders and/or concurrently, and withother acts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the methods in accordancewith the disclosed subject matter. In addition, those skilled in the artwill understand and appreciate that the methods could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be appreciated that the methodsdisclosed in this specification are capable of being stored on anarticle of manufacture to facilitate transporting and transferring suchmethods to computing devices. The term article of manufacture, as usedherein, is intended to encompass a computer program accessible from anycomputer-readable device or storage media.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system, in accordance with someimplementations of the present disclosure. The computer system 500(e.g., machine) may correspond to host computer system 100 of FIG. 1. Inembodiments of the present invention, the machine may be connected(e.g., networked) via network 580. The machine may be connected othermachines via network 580 in a Local Area Network (LAN), an intranet, anextranet, or the Internet. The machine may operate in the capacity of aserver or a client machine in a client-server network environment, or asa peer machine in a peer-to-peer (or distributed) network environment.The machine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, switch or bridge, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle machine is illustrated, the term “machine” shall also be taken toinclude any collection of machines (e.g., computers) that individuallyor jointly execute a set (or multiple sets) of instructions to performany one or more of the methodologies discussed herein.

The exemplary computer system 500 includes a processing device 502, amain memory 504 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM) or RambusDRAM (RDRAM), etc.), a static memory 506 (e.g., flash memory, staticrandom access memory (SRAM), etc.), and a secondary memory 516 (e.g., adata storage device), which communicate with each other via a bus 508.

The processing device 502 represents one or more general-purposeprocessors such as a microprocessor, central processing unit, or thelike. The term “processing device” is used herein to refer to anycombination of one or more integrated circuits and/or packages thatinclude one or more processors (e.g., one or more processor cores).Therefore, the term processing device encompasses a single core CPU, amulti-core CPU and a massively multi-core system that includes manyinterconnected integrated circuits, each of which may include multipleprocessor cores. The processing device 502 may therefore includemultiple processors. The processing device 502 may include a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Theprocessing device 502 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like.

The computer system 500 may further include a network interface device522. The computer system 500 also may include a video display unit 510(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 512 (e.g., a keyboard), a cursor controldevice 514 (e.g., a mouse), and a signal generation device 520 (e.g., aspeaker).

The secondary memory 516 may include a machine-readable storage medium(or more specifically a computer-readable storage medium) 524 on whichis stored one or more sets of instructions 554 embodying any one or moreof the methodologies or functions described herein (e.g., host networkanalyzer component 168A-C). The instructions 554 may also reside,completely or at least partially, within the main memory 504 and/orwithin the processing device 502 during execution thereof by thecomputer system 500; the main memory 504 and the processing device 502also constituting machine-readable storage media.

While the computer-readable storage medium 524 is shown in an exemplaryembodiment to be a single medium, the term “computer-readable storagemedium” should be taken to include a single medium or multiple media(e.g., a centralized or distributed database, and/or associated cachesand servers) that store the one or more sets of instructions. The term“computer-readable storage medium” shall also be taken to include anymedium other than a carrier wave that is capable of storing or encodinga set of instructions for execution by the machine that cause themachine to perform any one or more of the methodologies of the presentinvention. The term “computer-readable storage medium” shall accordinglybe taken to include, but not be limited to, non-transitory media such assolid-state memories, and optical and magnetic media.

The modules, components and other features described herein (for examplein relation to FIG. 1) can be implemented as discrete hardwarecomponents or integrated in the functionality of hardware componentssuch as ASICS, FPGAs, DSPs or similar devices. In addition, the modulescan be implemented as firmware or functional circuitry within hardwaredevices. Further, the modules can be implemented in any combination ofhardware devices and software components, or only in software.

Some portions of the detailed descriptions which follow are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “querying”, “receiving”,“generating”, “causing”, “simulating”, “analyzing”, or the like, referto the action and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

Embodiments of the present invention also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer system selectively programmed by a computer programstored in the computer system. Such a computer program may be stored ina computer readable storage medium, such as, but not limited to, anytype of disk including floppy disks, optical disks, CD-ROMs, andmagnetic-optical disks, read-only memories (ROMs), random accessmemories (RAMs), EPROMs, EEPROMs, magnetic disk storage media, opticalstorage media, flash memory devices, other type of machine-accessiblestorage media, or any type of media suitable for storing electronicinstructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear as set forth in thedescription above. In addition, the present invention is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the invention as described herein.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. Although the present invention has been describedwith reference to specific exemplary embodiments, it will be recognizedthat the invention is not limited to the embodiments described, but canbe practiced with modification and alteration within the spirit andscope of the appended claims. Accordingly, the specification anddrawings are to be regarded in an illustrative sense rather than arestrictive sense. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: querying, by a processingdevice, a host computer system for network configuration data associatedwith network components within the host computer system, whereinquerying the host computer system comprises querying an applicationcontainer of the host computer system for the network configuration dataof one or more of the network components within the applicationcontainer; receiving, in response to the querying, the networkconfiguration data comprising first configuration data of the networkcomponents within the host computer system and second configuration dataof connectivity between the network components within the host computersystem, wherein at least one of the network components is represented bya virtual network component within the application container of the hostcomputer system; and generating, in view of the network configurationdata, a network configuration model of the network components within thehost computer system, wherein the network components within the hostcomputer system are represented by nodes of a graph and the connectivityis represented by edges of the graph, wherein the virtual networkcomponent within the application container is represented by arespective node of the network configuration model, and wherein thenetwork configuration model logically groups the one or more of thenetwork components that are within the application container.
 2. Themethod of claim 1, wherein querying the host computer system for networkthe configuration data associated with network components within thehost computer system comprises: querying at least one of a hostoperating system (OS), a guest OS, or a hypervisor for the networkconfiguration data for the virtual network component within theapplication container.
 3. The method of claim 1, wherein the virtualnetwork component is provided by one of a virtual network interface card(vNIC) associated with the application container or a virtual networksegment associated with the vNIC.
 4. The method of claim 1, furthercomprising: causing a graphical representation of the networkconfiguration model to be displayed on a user device.
 5. The method ofclaim 1, further comprising: simulating network traffic on the hostcomputer system using the network configuration model.
 6. The method ofclaim 1, further comprising: analyzing a network configuration on thehost computer system using the network configuration model.
 7. Themethod of claim 1, wherein querying the host computer system for thenetwork configuration data associated with the network components withinthe host computer system further comprises: receiving an identifier ofthe application container operating on the host computer system;querying the host computer system for the first configuration data ofthe network components within the application container; and queryingthe host computer system for the second configuration data of theconnectivity between the network components within the applicationcontainer.
 8. The method of claim 1, wherein the application containeris a virtual machine.
 9. The method of claim 1, wherein the networkconfiguration model reflects at least one of a data link layer (layer 2)or a network layer (layer 3) of an Open Systems Interconnection (OSI)model.
 10. The method of claim 1, wherein the connectivity represents atleast one of: a path of a network frame between at least two OpenSystems Interconnection (OSI) data link layer (layer 2) networkcomponents or a path of a data packet between at least two OSI networklayer (layer 3) network components.
 11. A system comprising: a memory tostore instructions for a host network analyzer component; a processingdevice, coupled with the memory, to execute the instructions; and thehost network analyzer component, executed by the processing device, to:query, by the processing device, a host computer system for networkconfiguration data associated with network components within the hostcomputer system, wherein to query the host computer system theprocessing device to query an application container of the host computersystem for the network configuration data of one or more of the networkcomponents within the application container; receiving, in response tothe querying, the network configuration data comprising firstconfiguration data of the network components within the host computersystem and second configuration data of connectivity between the networkcomponents within the host computer system, wherein at least one of thenetwork components is represented by a virtual network component withinthe application container of the host computer system; and generate, inview of the network configuration data, a network configuration model ofthe network components within the host computer system, wherein thenetwork components within the host computer system are represented bynodes of a graph and the connectivity is represented by edges of thegraph, wherein the virtual network component within the applicationcontainer is represented by a respective node of the networkconfiguration model, and wherein the network configuration modellogically groups the one or more of the network components that arewithin the application container.
 12. The system of claim 11, wherein toquery the host computer system for network the configuration dataassociated with network components within the host computer system, theprocessing device further to: query at least one of a host operatingsystem (OS), a guest OS, or a hypervisor for the network configurationdata for the virtual network component within the application container.13. The system of claim 11, the processing device further to: cause agraphical representation of the network configuration model to bedisplayed on a user device.
 14. The system of claim 11, wherein to querythe host computer system for the network configuration data associatedwith the network components within the host computer system, theprocessing device further to: receive an identifier of the applicationcontainer operating on the host computer system; query the host computersystem for the first configuration data of the network components withinthe application container; and query the host computer system for thesecond configuration data of the connectivity between the networkcomponents within the application container.
 15. The system of claim 11,wherein the virtual network component is provided by one of a virtualnetwork interface card (vNIC) associated with the application containeror a virtual network segment associated with the vNIC.
 16. Anon-transitory computer readable storage medium, having instructionsstored therein, which when executed, cause a processing device to:query, by the processing device, a host computer system for networkconfiguration data associated with network components within the hostcomputer system, wherein to query the host computer system theprocessing device to query an application container of the host computersystem for the network configuration data of one or more of the networkcomponents within the application container; receiving, in response tothe querying, the network configuration data comprising firstconfiguration data of the network components within the host computersystem and second configuration data of connectivity between the networkcomponents within the host computer system, wherein at least one of thenetwork components is represented by a virtual network component withinthe application container of the host computer system; and generate, inview of the network configuration data, a network configuration model ofthe network components within the host computer system, wherein thenetwork components within the host computer system are represented bynodes of a graph and the connectivity is represented by edges of thegraph, wherein the virtual network component within the applicationcontainer is represented by a respective node of the networkconfiguration model, and wherein the network configuration modellogically groups the one or more of the network components that arewithin the application container.
 17. The non-transitory computerreadable storage medium of claim 16, wherein to query the host computersystem for network the configuration data, the processing device furtherto: query at least one of a host operating system (OS), a guest OS, or ahypervisor for the network configuration data for the virtual networkcomponent within the application container.
 18. The non-transitorycomputer readable storage medium of claim 16, the processing devicefurther to: cause a graphical representation of the networkconfiguration model to be displayed on a user device.
 19. Thenon-transitory computer readable storage medium of claim 16, wherein toquery the host computer system for the network configuration data, theprocessing device further to: receive an identifier of the applicationcontainer operating on the host computer system; query the host computersystem for the first configuration data of the network components withinthe application container; and query the host computer system for thesecond configuration data of the connectivity between the networkcomponents within the application container.
 20. The non-transitorycomputer readable storage medium of claim 16, wherein the virtualnetwork component is provided by one of a virtual network interface card(vNIC) associated with the application container or a virtual networksegment associated with the vNIC.